DeepPict is a “better picture item” for dialogs. With DeepPict, you can have different depths (including 1-bit) pictures and have DeepPict select the right one for the monitor(s) it is displayed on. DeepPict does work across multiple monitors. DeepPict is small (2.5K).
By default, DeepPict will use two PICTs, one for 1-3 bit monitors and another for 4-bit and higher. You can modify this behaviour with a PIC# resource (see below).
What else?
DeepPict has the following variants (and combinations thereof):
Variant 1: Always returns 0 to TestControl, thereby avoiding redraws over any overlapping items.
Variant 2: Reserved,
Variant 4: Reserved.
Variant 8: Unused
See the demo file with ResEdit or (better yet) Resorcerer,
DeepPict supports automatic 1-2 (BW) and 3-above (Color) without any extra resources. The one-bit PICT should be just before the colour PICT in ResNums. You may either store the ResNum in the control’s maximum field or use the name of the control to choose the PICTs by setting contrlMax zero.
DeepPict loads and releases the PICTs as necessary. With a ‘PIC#’ resource, you can have DeepPict load the PICTs for various depths you choose. When finding a PICT, DeepPict looks at (DepthOfCurrentMonitor & DepthMask) in the template. If no match is found, DeepPict will use the first PICT in the PIC# (which should be B&W if you want to support old Macs without ColourQD).
Tbe loading and releasing of PICTs can be dangerous. If you have multiple instances of a DeepPict control using the same PICT, make sure it uses a PIC#, so DeepPict can logon/logoff the usages. While not in use, PICTs are made purgeable.
Can I use (distribute) it?
Sure.
What's the catch?
22 :-)
A credit is due somewhere visible containing the following string:
